Cronos Bridge

Cronos Bridge is a set of routes and contracts that move value between Cronos's two native chains and, via third-party protocols, external networks. The canonical native route connects Cronos POS (Cosmos SDK, Bech32 cro addresses, chain ID crypto-org-chain-mainnet-1) with Cronos EVM (Ethereum-style 0x accounts, EIP-155 chain ID 25, Cosmos chain ID cronosmainnet_25-1); an EIP-155 chain ID distinguishes the EVM network when a wallet signs a transaction. CRO is the gas token on both sides.

Third-party bridges like Stargate, Relay, and Symbiosis reach additional networks but use different contracts and trust models than the native route. Cronos zkEVM has its own bridge and is not the same thing as the Cronos POS–Cronos EVM route, so the route name and destination chain must match what you intend to use.

Bridging starts when you select the source chain, destination chain, asset, amount, and receiving wallet, connect a compatible self-custody wallet, and sign a single source-chain transaction. The site never needs your seed phrase or private key.

On native Cronos routes, the mechanics are IBC: the source chain escrows or converts the asset, relayers carry a proof of that event to the destination chain, and the destination chain independently verifies the proof before releasing or minting the destination representation. Relayers only deliver messages — they can't forge them, because the destination chain does its own verification; this IBC packet flow is the core mechanism. On EVM-side token interactions you may also sign an approval before the bridge transaction itself; that approval controls which token amount the bridge contract can move.

Depositing means signing on the source chain and waiting for confirmation, relay, and destination execution; on native Cronos routes this typically completes in minutes, depending on both chains being healthy and relayers being available. Supported assets are allow-listed, so a token absent from the live interface is not supported on that route regardless of what a third-party site claims.

The receiving address must use the destination chain's format: Cronos POS expects a Bech32 cro address, while Cronos EVM expects a 0x address. Bech32 format is a human-readable encoding used by some blockchain addresses. Sending to the right chain with the wrong address format is a recoverable-looking mistake that often isn't, and you need CRO on the destination side to use the funds when they arrive.

Withdrawing is the same flow in reverse, and the return leg can take longer in some configurations because routes with proving or finalization steps wait until the source chain's state is considered final on the destination side. Deposit-side speed is not a timing estimate for withdrawal.

For a pending withdrawal, keep the source transaction hash and follow the route status; a second submission can double-pay gas or lock funds into a second in-flight transfer. If the interface reports completion, verify the balance on the destination chain before treating it as spendable.

Bridge cost is source-chain gas plus any route-specific provider charge: on native IBC routes, destination-side mechanism costs are handled by relayers and module execution rather than a separate user-facing toll. Since CRO is the gas token on both Cronos EVM and Cronos POS, you need CRO wherever you intend to transact; bridging from an external network also requires that chain's gas. The technical gas overview explains why the source transaction needs a fee.

Third-party bridges add provider fees for liquidity and routing, and the amount varies by route, asset, and market conditions. Compare the quoted receive amount in the interface before signing. Native routes typically settle in minutes, but confirmation depth, relayer availability, and channel health on both chains gate completion.

Cronos Bridge removes custodial exchange risk because your wallet holds the signing keys, while protocol modules escrow, release, or convert assets rather than a company holding them. Smart-contract bugs, compromised approvals, relayer or channel failures, and plain user error still remain live risks; open-source Cronos code permits inspection but does not guarantee outcomes.

Phishing is a separate wallet-drain risk: fake bridge sites clone the interface and use malicious approvals, and phishing guidance describes the same impersonation pattern. A mismatched domain, an approval for unlimited spend on an unrelated token, or a request for your recovery phrase is a stop signal; verify the domain, networks, asset, and recipient in the wallet's signing prompt, use a small test transfer the first time you use a route, and cross-check contract and transaction details on the relevant explorer.

Wrong network. Switch the wallet to the chain selected in the route; the interface cannot build a transaction for a different network.

Funds arrived but unusable. Add CRO on Cronos EVM or Cronos POS before trying to move the destination balance; the destination gas asset is required for the next transaction. Bridge a small amount of CRO first next time, or acquire gas through a route that delivers it.

Transfer pending. Check the source transaction on the relevant explorer, confirm it succeeded, and then follow the relay step until the source transaction is final; completion depends on both chains, confirmations, relayer availability, and channel health.